Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move all private functions to use an anonymous namespace. #233

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

clalancette
Copy link
Collaborator

This is just so we consistently use C++-style anonymous namespaces, instead of C-style "static" functions. No functional change.

This should fix #124

This is just so we consistently use C++-style anonymous namespaces,
instead of C-style "static" functions.  No functional change.

Signed-off-by: Chris Lalancette <[email protected]>
@Yadunund Yadunund merged commit 568c0c3 into rolling Jul 1, 2024
8 checks passed
@Yadunund Yadunund deleted the clalancette/anonymous-namespace branch July 1, 2024 21:31
@Timple
Copy link
Contributor

Timple commented Jul 1, 2024

Just curious, what changed your mind with regards to the preference for static?

@clalancette
Copy link
Collaborator Author

Just curious, what changed your mind with regards to the preference for static?

We just had more anonymous functions, so it was less work to convert static -> anonymous rather than anonymous -> static.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Revisit anonymous namespaces vs. static functions
3 participants